home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: munta.cs.mu.OZ.AU!fjh
- From: fjh@munta.cs.mu.OZ.AU (Fergus Henderson)
- Subject: Re: Name-mangling standard
- Message-ID: <9601219.10685@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU (CS-Usenet)
- Organization: Computer Science, University of Melbourne, Australia
- References: <20c.32169.607@newage.com.ar> <4bsnbu$5mu@mujibur.inmind.com> <30EDC013.7C780E5E@cims.nyu.edu> <DL1pqE.KKq@infosoft.com>
- Date: Fri, 12 Jan 1996 08:14:30 GMT
-
- jgalt@infosoft.com (John Galt) writes:
-
- >> I certainly hope not! Name mangling is a solution to passing type
- >> information to 1950's linkers. Once linkers become more sophisticated,
- >> name mangling can disappear back into the slime from which it came.
- >
- >I beg to differ. Name mangling serves several indispensible functions:
-
- The functions it serves may be indispensible, but name mangling itself
- is not. If linkers simply allowed arbitrary characters in symbol names
- (just as many modern operating systems allow almost arbitrary
- characters in file names) then all three functions that you listed
- could be done without name mangling.
-
- >In short, wanting to eliminate name mangling is like wanting a compiler that
- >never prints error messages. It's for people who would rather walk off a
- >cliff than have someone tell them they're about to.
-
- No, I think you missed the point. Wanting to eliminate name mangling
- is for people who would rather hear "you're about to fall off a cliff!"
- than "youX27reX20aboutX20toX20fallX20offX20aX20cliffX21".
-
- --
- Fergus Henderson WWW: http://www.cs.mu.oz.au/~fjh
- fjh@cs.mu.oz.au PGP: finger fjh@128.250.37.3
-